>In article <3c0f56d1.1535610@news.povray.org> , ken### [at] uniplanit (Angelo 
>'kENpEX' Pesce) wrote:
>
>> I'm not depressed at all... But since it's impossible to see a tech
>> faq, a document about inner workings, a to-do or a wish list and
>> everything seems so "secret" to me, how could I know that those where
>> already features somewhat planned or that pov-team was aware of
>> them?????
>The source code is open for you to see, so there is no secret.
I know what there is into povray, I wanted to know where povray will
go...

>I think this thread alone is a very good example to explain why there is no
>completely open discussion of the development of POV-Ray or a completely
>open development.  There would simply be too many people who only tell those
>who actually implement feature that something is easy or that it should be
>implemented this way or that way.  However, so rarely do the people who do
>all the discussion actually do any work.  They just keep everyone from
>working while contributing nothing usable.

I agree with you... you're right... But an interface between povray
team and povray users is necessary, otherwise how can U know that a
feature is more or less wanted? The first problem that I see is that I
can't know the future of povray development... I U tell me, we are the
developers, we will do x,y,z and we can't change our mind now, if U
want p,q,r do it yourself I can accept this. But if I don't know what
are the plans for the next povray how can I make a good choice?
Better, I think povray team should tell via a faq that:
we will do x,y,z
we are thinking to do l,m,n but it's hard because of...
we will not do p,q,r because of...
if U want that do it yourself
So I will know not only what you're doing but also why you're not
doing something else, and I can propose U to do things only if they
are not in the todo/nottodo list... Also if I have (I or someone else
this is obvious) an idea on the l,m,n things that solve a problem and
make them more easy, I can tell U... Is this wise? I think so...

>To summarize my, and only my opinion, which has been formed based on the
>many, many discussion that went like this one, from the newbies with three
>month of programming experience thinking they can help, from those who
>distributed some of the messiest source code I have seen as patch for
>POV-Ray, I say:
>With the kind of help that is offered it will be really difficult to adopt a
>more open development model for POV-Ray 4.0.  With public contributions of
>the current quality, unless constantly verified by others (read: the
>POV-Team) we would end up with an insane mess and nothing remotely useable
>as a ray-tracer.

I'm not a povray developer so I can't discuss about that. I don't care
to discuss about that too. there are many "open" projects, povray is a
bit more "closed" but hey, that's not my project, I can't decide...

>Yes, this is my opinion. I won't change it. I am just letting everybody know
>what I see as a major problem.
>    Thorsten
>
>____________________________________________________
>Thorsten Froehlich, Duisburg, Germany
>e-mail: tho### [at] trfde
>
>Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message